The [method@TabView.close_page_finish] call doesn't have to happen inside
the handler, so can be used to do asynchronous checks before confirming the
closing.
A typical reason to connect to this signal is to show a confirmation dialog
for closing a tab.
Emitted after [method@TabView.close_page] has been called for @page.
The handler is expected to call [method@TabView.close_page_finish] to confirm or reject the closing.
The default handler will immediately confirm closing for non-pinned pages, or reject it for pinned pages, equivalent to the following example:
The [method@TabView.close_page_finish] call doesn't have to happen inside the handler, so can be used to do asynchronous checks before confirming the closing.
A typical reason to connect to this signal is to show a confirmation dialog for closing a tab.